When using IE PC, Firefox PC/Mac the request_content field contains the HTML encoded form data. I noticed today that the request_content field when using the Safari browser is much different. Unfortunately I can not say exactly when the processing of this field changed but I do know that it was not always this way. Firefox still works the same for both the Mac and PC. If anyone out there is parsing the request_content field for the data pairs they should know that the information received from Safari will need to be parsed differently. If anyone knows of a workaround other than 2 parsing routines please share. Hope this helps someone. ~R Example Data Safari / Mac ------------0xKhTmLbOuNdArY Content-Disposition: form-data; name="chkmulti" 9A07AD1FAE23B4338525728A007AB88D ------------0xKhTmLbOuNdArY Content-Disposition: form-data; name="chkmulti" 08F6A355F98899AD8525728A007B48CB ------------0xKhTmLbOuNdArY IE / Firefox {PC & Mac} &chkmulti=9A07AD1FAE23B4338525728A007AB88D&chkmulti=08F6A355F98899AD8525728A007B48CB
Go back